-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS] Add steps for fixing aliases and names in the CMS for term changes #16808
Conversation
@@ -75,5 +75,10 @@ body: | |||
- [ ] Content is reviewed by relevant stakeholders | |||
- [ ] (List any necessary review and approval steps here) | |||
- [ ] Term is published | |||
If term is a VA Service: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"If term is part of VA Service Taxonomy & the term name changes:"
Suggested for more specificity. This template is also used when updating an existing term without the term name changing so won't always apply."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great suggestion. I just update the PR.
861ca9d
to
eac88d6
Compare
Description
Relates to this Slack thread
Testing done
Screenshots
QA steps
What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?
As user facilities team member
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing
Is this PR blocked by another PR?
DO NOT MERGE
Does this PR need review from a Product Owner
Needs PO review
CMS user-facing announcement
Is an announcement needed to let editors know of this change?